Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1532

reference: 169-tree-1
name: 1532
tree-preservation-order: undefined
169-tpo-1
uprn
address-text
point: POINT (-0.940847 50.865759)
geometry: MULTIPOLYGON (((-0.940804 50.865754,-0.940806 50.865763,-0.940812 50.865770,-0.940821 50.865776,-0.940833 50.865780,-0.940846 50.865782,-0.940871 50.865777,-0.940881 50.865771,-0.940887 50.865763,-0.940890 50.865755,-0.940888 50.865747,-0.940882 50.865739,-0.940872 50.865733,-0.940861 50.865729,-0.940848 50.865728,-0.940834 50.865729,-0.940822 50.865732,-0.940813 50.865738,-0.940807 50.865746,-0.940804 50.865754)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL